comment

diff --git a/doc/bugs/windows__58___needlessly_reminded_to_run___96__restage__96__/comment_1_e738eb3d45bb7c4baa0a5c88cdf7a40a._comment b/doc/bugs/windows__58___needlessly_reminded_to_run___96__restage__96__/comment_1_e738eb3d45bb7c4baa0a5c88cdf7a40a._comment
new file mode 100644 (file)
index 0000000..a5594e6
--- /dev/null
+++ b/doc/bugs/windows__58___needlessly_reminded_to_run___96__restage__96__/comment_1_e738eb3d45bb7c4baa0a5c88cdf7a40a._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1t"""
+ date="2022-09-30T17:24:27Z"
+ content="""
+Not sure this is quite the same situation, but on linux, I am seeing
+`git-annex unlock` of a locked file display the warning.
+
+Also, .git/annex/restage.log is left empty after the command completes.
+Which seems to indicate it managed to restage the file after all. Is that
+file empty for you on windows after it displays the warning and before
+running other commands?
+"""]]